Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/__tests__/renderer/components/ui/Spinner.test.tsx`:
- Around line 12-32: Tests are failing because the Spinner component does not
expose data-testid="loader2-icon" while the tests (Spinner.test.tsx) query that
id; update the Spinner component (Spinner in
src/renderer/components/ui/Spinner.tsx) to add data-testid="loader2-icon" to the
rendered icon element (the same element that receives className, style/size and
color props) so the test queries (screen.getByTestId('loader2-icon')) find the
element, ensuring the component still applies className, size, and color props
to that element.

In `@src/renderer/components/AgentSessionsBrowser.tsx`:
- Around line 732-739: The icon-only GhostIconButton used to trigger
clearViewingSession lacks accessible naming; update the GhostIconButton instance
(the one rendering ChevronLeft and calling clearViewingSession) to include an
accessible label by adding an ariaLabel (e.g., "Back" or "Close session") and a
title prop so screen readers and tooltips can announce the button; ensure the
label accurately describes the action (e.g., ariaLabel="Go back to session
list") and keep the existing onClick and styling unchanged.

In `@src/renderer/components/AgentSessionsModal.tsx`:
- Around line 449-457: The GhostIconButton used as the icon-only back control in
AgentSessionsModal lacks an accessible name; update the GhostIconButton
invocation (the instance rendering ChevronLeft inside AgentSessionsModal) to
include an accessible label (e.g., aria-label="Back" or aria-label="Go back to
sessions" and optionally title="Back") so assistive technology can announce the
control; keep the existing onClick behavior that calls setViewingSession(null)
and setMessages([]).
- Around line 601-604: The empty-state title in AgentSessionsModal currently
hardcodes “Claude” (the ternary setting for title when sessions.length === 0);
change it to a provider-agnostic message or use the modal's provider variable
(e.g., providerName or session.provider) so the text reads generically like "No
sessions found for this project" or interpolates the current provider
dynamically; update the title prop in the AgentSessionsModal render branch that
references sessions to use the generic string or the provider variable instead
of the literal "Claude".

In `@src/renderer/components/CreatePRModal.tsx`:
- Around line 233-235: The close button is an icon-only control
(GhostIconButton) with no accessible name; update the GhostIconButton instance
used for closing the CreatePRModal to include an accessible label (e.g.,
ariaLabel="Close create pull request modal" or aria-label="Close") so assistive
tech can identify it; add the prop to the GhostIconButton wrapping the X icon
(the onClose handler stays unchanged) and use a clear, concise label like
"Close" or "Close create PR modal".

In `@src/renderer/components/CreateWorktreeModal.tsx`:
- Around line 143-145: The close button is icon-only and lacks an accessible
name; update the GhostIconButton element (the instance with onClose and child X)
to provide an accessible label (e.g., add aria-label="Close" and a matching
title="Close" or include visually hidden text) so screen readers can announce
it; ensure the label text is concise and localized if needed and keep the
onClick handler (onClose) unchanged.

In `@src/renderer/components/DirectorNotes/DirectorNotesModal.tsx`:
- Around line 215-217: The close button rendered with GhostIconButton (wrapping
the X icon and invoking onClose) lacks an accessible name; update the
GhostIconButton usage to include an aria-label (e.g., aria-label="Close" or a
localized string like aria-label={t('close')}) and also add a title attribute if
a tooltip is desired so screen readers and sighted users get a clear label;
ensure you set the attribute on the GhostIconButton element (not on the X icon)
to preserve existing behavior.

In `@src/renderer/components/LeaderboardRegistrationModal.tsx`:
- Around line 801-803: The GhostIconButton used for closing (the element with
onClick={onClose} containing the <X /> icon) is icon-only and lacks an
accessible name; update the GhostIconButton invocation to provide an explicit
accessible label by adding an ariaLabel (or aria-label) prop such as "Close"
(and optionally a title prop) so screen readers can announce its purpose,
ensuring the button still uses theme.colors.textDim for styling.

In `@src/renderer/components/MainPanel/MainPanelHeader.tsx`:
- Around line 225-236: The GhostIconButton used to copy the branch name (the
component wrapping the Copy icon and calling copyToClipboard with
gitInfo.branch) relies only on the title prop for accessibility; add an explicit
ariaLabel prop (e.g., "Copy branch name") to GhostIconButton so the icon-only
control has a proper accessible name for screen readers, keeping the existing
title and click behavior intact.

In `@src/renderer/components/Settings/SshRemoteModal.tsx`:
- Around line 764-771: The icon-only GhostIconButton used to remove env vars
(the one wrapping <Trash2 /> and calling removeEnvVar(entry.id)) needs an
explicit accessible name: add an ariaLabel prop (or aria-label if that is the
component API) with a descriptive string such as "Remove variable" plus the
variable identifier (e.g., entry.key or entry.id) so screen readers can announce
which variable will be removed when the button is activated.

In `@src/renderer/components/ShortcutsHelpModal.tsx`:
- Around line 75-77: The GhostIconButton used for closing the ShortcutsHelpModal
is icon-only and lacks an accessible name; update the JSX for GhostIconButton
(the instance with props onClose and child <X className="w-4 h-4" />) to include
an ariaLabel (e.g., ariaLabel="Close shortcuts help" or similar) and optionally
a title prop with the same text so screen readers and tooltips have a clear
label; ensure the ariaLabel string is concise and descriptive of the control's
action.

In `@src/renderer/components/TransferProgressModal.tsx`:
- Around line 386-393: The close-handler currently uses onComplete?.() ||
onCancel(), which calls onCancel after onComplete because onComplete returns
void (falsy); change the handler in TransferProgressModal's GhostIconButton so
it conditionally calls onComplete if defined else calls onCancel (e.g., if
(onComplete) { onComplete(); } else { onCancel(); }) ensuring only one callback
runs when the close button is clicked; update references to onComplete and
onCancel in that GhostIconButton onClick prop accordingly.

In `@src/renderer/components/UpdateCheckModal.tsx`:
- Around line 195-197: The GhostIconButton rendering the close icon
(GhostIconButton with onClose and inner <X />) is missing an accessible label;
update the GhostIconButton usage in UpdateCheckModal to include an explicit
aria-label (e.g., "Close update modal") or ariaLabel prop (or title) so screen
readers can identify the control, ensuring the close action remains wired to
onClose and the icon (<X />) is unchanged.

In `@src/renderer/components/WorktreeConfigModal.tsx`:
- Around line 209-211: The close icon button in WorktreeConfigModal uses
GhostIconButton with only an <X /> icon and no accessible name; update the
GhostIconButton where it is rendered (the element with props onClick={onClose}
and child <X />) to include an explicit accessible name by adding an aria-label
(e.g., aria-label="Close") or a title prop so screen readers can announce it;
ensure the prop key matches GhostIconButton's API (aria-label or title) so
accessibility tools receive the label.

---

Outside diff comments:
In `@src/renderer/components/SymphonyModal.tsx`:
- Around line 712-719: The header for "Available Issues" contains an unreachable
loading indicator: remove the conditional JSX `{isLoadingIssues && <Spinner
size={12} color={theme.colors.accent} />}` in the h4 (the Available Issues
header) because `isLoadingIssues` is already routed to the skeleton path
earlier; update the component (SymphonyModal.tsx) to simply render the header
text and count (availableIssues.length) without that spinner conditional.

---

Nitpick comments:
In `@src/renderer/components/AutoRun/AutoRunExpandedModal.tsx`:
- Around line 422-424: The close button relies on a title for accessible naming;
update the GhostIconButton instance used with the onClick handler handleClose
and icon X to include an explicit ariaLabel prop (e.g., ariaLabel="Close") so
screen readers get a consistent name rather than depending on the tooltip/title;
ensure the ariaLabel string matches other close buttons in the component for
consistency.

In `@src/renderer/components/DocumentsPanel.tsx`:
- Around line 488-490: The close button is icon-only and needs an accessible
name: update the GhostIconButton usage (the one with onClose and the X icon) to
pass an explicit accessible label like aria-label="Close" (and optional
title="Close") so screen readers can announce the control; ensure the props are
added to the GhostIconButton component invocation that currently renders
<GhostIconButton onClick={onClose} color={theme.colors.textDim}> with the X icon
inside.

In `@src/renderer/components/PlaygroundPanel.tsx`:
- Around line 599-601: The close button in PlaygroundPanel is icon-only
(GhostIconButton with X) and needs an accessible name; update the
GhostIconButton instantiation in PlaygroundPanel.tsx to pass an accessible-name
prop (e.g., ariaLabel or aria-label depending on the GhostIconButton prop API)
such as "Close playground" and keep the existing onClose and color props so
assistive tech can announce the action reliably.

In `@src/renderer/components/SendToAgentModal.tsx`:
- Around line 18-19: The send CTA in SendToAgentModal mixes two loader
components—use the shared Spinner instead of Loader2 to standardize UI; update
the send button render path in the SendToAgentModal component to import and
render Spinner (already imported at top) wherever Loader2 is used (e.g., the
send CTA/submit handler render branch), remove the Loader2 usage and any related
imports, and ensure Spinner receives the same props (size/weight/className) used
by Loader2 so styling and behavior remain consistent.

In `@src/renderer/components/Settings/EnvVarsEditor.tsx`:
- Around line 194-201: The GhostIconButton used for removing env var entries
(the element rendering Trash2 with onClick={() => removeEntry(entry.id)}) is
icon-only and should include an accessible label; add an ariaLabel prop (e.g.,
ariaLabel="Remove variable") to the GhostIconButton so screen readers reliably
announce the action, keeping the existing title and styling intact and ensuring
the removeEntry(entry.id) handler remains unchanged.

In `@src/renderer/components/ui/GhostIconButton.tsx`:
- Around line 31-32: The GhostIconButton component currently allows an icon-only
button to be rendered without an accessible name; update the rendered element to
set aria-label to a fallback value by using the props ariaLabel || title (i.e.,
when ariaLabel is absent use title) so the button always has an accessible name,
and ensure the title prop is preserved on the element; locate GhostIconButton
and change where aria-label is assigned to use ariaLabel ?? title (or ariaLabel
|| title) for both occurrences referenced (around the ariaLabel prop and the
other usage).

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/renderer/components/AgentSessionsBrowser.tsx`:
- Around line 741-761: The GhostIconButton instances used for starring sessions
(the component rendering Star and calling toggleStar with
viewingSession.sessionId and using title prop) lack explicit accessible names;
add an ariaLabel prop to each icon-only GhostIconButton (set it to the same
string as the title, i.e., "Add to favorites" or "Remove from favorites" based
on starredSessions.has(viewingSession.sessionId)) so screen readers receive an
explicit label; apply the same change to the other GhostIconButton occurrences
handling session actions in the same file that use icon-only buttons.

In `@src/renderer/components/TransferProgressModal.tsx`:
- Around line 387-393: The click handler duplicates logic present in
handlePrimaryClick; replace the inline onClick block in TransferProgressModal
(currently calling onComplete() or onCancel()) with a call to handlePrimaryClick
to reuse the shared behavior and avoid branching duplication—ensure
handlePrimaryClick is accessible in the component scope and that it performs the
same onComplete/onCancel decision so behavior remains unchanged.